Software Development
Software Project Requirements and Design with Agile
Agile Software Projects: Estimation Methods
it_agsrddj_03_enus
Agile Software Projects: Software Design
it_agsrddj_02_enus
Agile Software Projects: Software Requirements
it_agsrddj_01_enus
Agile Software Projects: Estimation Methods
Lesson Objectives
Agile Software Projects: Estimation Methods
- discover the key concepts covered in this course
- recognize the challenges faced in transforming to an Agile organization
- describe best practices to be adopted for building an Agile culture in the organization
- recognize how estimation in Agile involves every member of the team
- describe how to perform Agile estimation and some of the popular Agile estimation methods, including Story Points, Planning Poker, T-shirt Sizes, Dot Voting, and Bucket System
- describe how to use the Story Points estimation method in Agile
- describe how to use the Planning Poker estimation method in Agile
- describe how to use the Dot Voting estimation method in Agile
- describe how to use the Bucket System estimation method in Agile
- recognize the benefits offered by Agile estimation models over traditional estimation methods
- describe the key questions to consider when estimating
- describe some of the common pitfalls that occur using Agile estimation techniques
- illustrate through an example how to arrive at an estimate for a story point using Planning Poker
- summarize the key concepts covered in this course
Overview/Description
Software companies want predictability from their development teams in terms of software delivery, quality, and, just as importantly, cost. The Agile process makes development costs more predictable by promoting the breaking of work into small pieces so it can be accurately estimated by the Agile team. Organizations value Agile team members who are educated in efficient Agile estimation methods, as they make the cost of software projects more predictable and therefore less wasteful. In this course, you'll learn how Agile applies to the whole organization and needs to become part of the culture. Next, you'll learn why team involvement is important in the estimation process and various estimate techniques for determining the scope of work. Finally, you'll learn some of the key questions that should be asked during the estimation process and some of the pitfalls of using Agile estimation techniques.
Software companies want predictability from their development teams in terms of software delivery, quality, and, just as importantly, cost. The Agile process makes development costs more predictable by promoting the breaking of work into small pieces so it can be accurately estimated by the Agile team. Organizations value Agile team members who are educated in efficient Agile estimation methods, as they make the cost of software projects more predictable and therefore less wasteful. In this course, you'll learn how Agile applies to the whole organization and needs to become part of the culture. Next, you'll learn why team involvement is important in the estimation process and various estimate techniques for determining the scope of work. Finally, you'll learn some of the key questions that should be asked during the estimation process and some of the pitfalls of using Agile estimation techniques.
Target
Agile Software Projects: Software Design
Lesson Objectives
Agile Software Projects: Software Design
- discover the key concepts covered in this course
- describe using examples the best practices of using modularity in Agile software design
- describe using examples the best practices of using coupling concepts in Agile software design
- describe using examples the best practices of using cohesion concepts in Agile software design
- recognize how to build product vision from a requirement or objective of the software product
- illustrate through an example the effectiveness of using product vision board to define the product features
- recognize how Agile tools such as initiatives, themes, epics, and stories help define and manage scope better than traditional methods for scoping
- recognize how to generate user stories from a requirement or objective of the software product
- describe the minimal viable product
- define what the Definition of Done means in the Scrum framework using examples
- describe what UX design is and the principles of UX design
- recognize how to overcome the challenges of integrating Agile with UX design
- describe the best practices for Agile software requirement and design
- summarize the key concepts covered in this course
Overview/Description
Today's software companies are looking for people who know how to do more than just work in an Agile teams. They desire employees who can design software to work with the quick, demanding iteration cycles of the Agile process. In other words, they are looking for someone with Agile software design experience. Agile software design is a valuable skill since it complements the Agile team approach by focusing on making software more maintainable and minimizing complexity as software changes and scales. In this course, you'll learn about the concepts of modularity, coupling, and cohesion. You'll examine the product vision and using product vision boards. Next, you'll learn the purpose of Agile scoping tools, the concept of minimal viable product, and the Definition of Done. Finally, you'll learn about UX design and Agile design best practices.
Today's software companies are looking for people who know how to do more than just work in an Agile teams. They desire employees who can design software to work with the quick, demanding iteration cycles of the Agile process. In other words, they are looking for someone with Agile software design experience. Agile software design is a valuable skill since it complements the Agile team approach by focusing on making software more maintainable and minimizing complexity as software changes and scales. In this course, you'll learn about the concepts of modularity, coupling, and cohesion. You'll examine the product vision and using product vision boards. Next, you'll learn the purpose of Agile scoping tools, the concept of minimal viable product, and the Definition of Done. Finally, you'll learn about UX design and Agile design best practices.
Target
Agile Software Projects: Software Requirements
Lesson Objectives
Agile Software Projects: Software Requirements
- discover the key concepts covered in this course
- recognize what software requirements are and their importance in successful software project management
- describe what functional requirements are and how they are used in a software project
- describe what non-functional requirements are and how they are used in a software project
- recognize how functional requirements differ from non-functional requirements
- describe the importance of requirements management and list the four fundamental requirements management processes
- describe in detail the requirements management process
- illustrate through a non-example the shortcomings of traditional requirement specification and management process (ever-changing scope, wasted efforts, demotivated team, etc.)
- compare the benefits and features of traditional project management against Agile project management
- identify how the Agile approach helps define and manage software requirements
- describe the importance of Agile software requirements
- describe a typical software requirements specification document
- describe how the feasibility study tool helps determine whether a solution is practically achievable or not
- summarize the key concepts covered in this course
Overview/Description
Being able to gather software requirements quickly is a crucial component of the software development life cycle. Sadly, traditional software requirements are static and do not respond well to change and are not very effective. Agile software requirement methods can be used to create requirements that adapt to change and are highly effective in creating software that will satisfy customer needs. In this course, you'll learn the differences between software requirements, functional requirements, and non-functional requirements. You'll examine the shortcomings of traditional requirement specification and the traditional management process. Finally, you'll learn about Agile software management, Agile software requirements, the software requirements specification document, and the software feasibility tool.
Being able to gather software requirements quickly is a crucial component of the software development life cycle. Sadly, traditional software requirements are static and do not respond well to change and are not very effective. Agile software requirement methods can be used to create requirements that adapt to change and are highly effective in creating software that will satisfy customer needs. In this course, you'll learn the differences between software requirements, functional requirements, and non-functional requirements. You'll examine the shortcomings of traditional requirement specification and the traditional management process. Finally, you'll learn about Agile software management, Agile software requirements, the software requirements specification document, and the software feasibility tool.
Target
